home *** CD-ROM | disk | FTP | other *** search
- Path: airdmhor.gen.nz!not-for-mail
- From: gumboot@airdmhor.gen.nz (Simon Hosie)
- Newsgroups: comp.lang.c
- Subject: Re: void main() and other atrocities!
- Date: 7 Feb 1996 01:44:47 +1300
- Organization: Airdmhor
- Message-ID: <4f7ifv$8l4@airdmhor.gen.nz>
- References: <4eduaj$1aq@grouper.Exis.Net> <4epplj$egf@host-3.cyberhighway.net> <4erjn2INN38b@keats.ugrad.cs.ubc.ca> <9602021300.AA04359@dxmint.cern.ch> <4f2rahINNmud@keats.ugrad.cs.ubc.ca>
- NNTP-Posting-Host: airdmhor.gen.nz
- X-Newsreader: TIN [version 1.2 PL2]
-
- Kazimir Kylheku:
- > It's also atrocious that main() has to be treated as a special language
- > construct, and that a call to exit() in main() (when it is the last statement)
- > is to be identical to a return.
-
- It's already a special case in that the program starts there.
-
-
- > I did read the relevant section in the FAQ. It is merely concerned with the
- > issue of eliminating compiler warnings stemming from calling exit() in main()
- > despite a "void" declaration thereof. The issue that a void function may
- > not be compatible with a call to an int function doesn't seem that significant,
- > since nobody in their right mind would design a compiler that way.
-
- How about an operating system? Nah, they'd never make an operating system
- that expected a return value from a program, would they?
-